Skip to content

fix(assistants): load registered assistants from top-level config in setup flow#409

Open
alezander86 wants to merge 1 commit into
codemie-ai:mainfrom
alezander86:EPMCDME-13372_fix-registered-assistants-tab
Open

fix(assistants): load registered assistants from top-level config in setup flow#409
alezander86 wants to merge 1 commit into
codemie-ai:mainfrom
alezander86:EPMCDME-13372_fix-registered-assistants-tab

Conversation

@alezander86

@alezander86 alezander86 commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Summary

  • ConfigLoader.load() only merges profile-level data; after migration 004, codemieAssistants lives at the top-level MultiProviderConfig, not in profiles
  • config.codemieAssistants || [] always resolved to [], so the Registered tab in the CLI assistant selection panel always showed 0 assistants
  • Replace the profile-based read with loadRegisteredAssistants(), which correctly loads from both global and local top-level config with file verification

Test plan

  • Register an assistant as a skill via codemie assistants setup
  • Re-open the CLI assistant selection panel
  • Verify the Registered tab shows the previously registered assistant
  • Verify other tabs (Project, Marketplace) are unaffected
  • Verify behaviour with both global and local storage scopes

Fixes EPMCDME-13372

…setup flow

ConfigLoader.load() only merges profile-level data, which does not contain
codemieAssistants after migration 004 moved them to the top-level
MultiProviderConfig. This caused the Registered tab in the CLI assistant
selection panel to always show 0 assistants.

Replace the profile-based read with loadRegisteredAssistants(), which
correctly loads from both global and local top-level config with file
verification.

Fixes EPMCDME-13372
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants